Thanks for the pull request, @feoh!

What's next?

Please work through the following steps to get your changes ready for engineering review:

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

🔘 Update the status of your PR

Your PR is currently marked as a draft. After completing the steps above, update its status by clicking "Ready for Review", or removing "WIP" from the title, as appropriate.

🔘 Let us know that your PR is ready for review:

Who will review my changes?

This repository is currently maintained by @openedx/docs-openedx-org-maintainers. Tag them in a comment and let them know that your changes are ready for review.

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

Here is a list of new or updated feature flags added this release that we know of on the product side:

1. For libraries, here is a link to the configuration details for what we're adding to libraries this release: link
2. For the left-sidebar navigation, we aren't adding any new toggles or switches this release, but we are updating the default configuration of this waffle flag: courseware.enable_navigation_sidebar from False (in Redwood) to True in Sumac to enable the new Courseware Sidebar

Here is a list of new or updated feature flags added this release that we know of on the product side:

1. For libraries, here is a link to the configuration details for what we're adding to libraries this release: [link](https://github.com/openedx/frontend-app-authoring/issues/1334)

2. For the left-sidebar navigation, we aren't adding any new toggles or switches this release, but we are updating the default configuration of this waffle flag: courseware.enable_navigation_sidebar from False (in Redwood) to True in Sumac to enable the new Courseware Sidebar

Thank you! I added a line about the newly default enabled sidebar nav toggle. As to the library configuration stuff, not sure how much of that needs to be in the dev/ops section of the release notes. I'm assuming it will be covered elsewhere. Please let me know if I'm wrong about that, and give me some text you'd like to see added as I have no idea what to write for this otherwise.